-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
Test DocTestFinder directly instead of calling support.run_doctest() #108917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test DocTestFinder directly instead of calling support.run_doctest() #108917
Conversation
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
GH-109259 is a backport of this pull request to the 3.12 branch. |
…ythonGH-108917) (cherry picked from commit 0abc935) Co-authored-by: Serhiy Storchaka <[email protected]>
GH-109260 is a backport of this pull request to the 3.11 branch. |
…ythonGH-108917) (cherry picked from commit 0abc935) Co-authored-by: Serhiy Storchaka <[email protected]>
|
…test() (GH-108917) (GH-109260) (cherry picked from commit 0abc935) Co-authored-by: Serhiy Storchaka <[email protected]>
…test() (GH-108917) (#109259) Test DocTestFinder directly instead of calling support.run_doctest() (GH-108917) (cherry picked from commit 0abc935) Co-authored-by: Serhiy Storchaka <[email protected]>
It was the last use of
support.run_doctest()
.